Skip to content

Clean GH Actions workspace before each job #8574

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 19, 2020

Conversation

anatoliykmetyuk
Copy link
Contributor

@anatoliykmetyuk anatoliykmetyuk commented Mar 19, 2020

GH Actions mounts docker volumes and executes the jobs from
them. For some reason it doesn't clean these volumes
automatically after each run. We assume that each run happens
on a clean workspace and hence there are weird consequences
when this assumption is broken.

One of them, for example, is failure to publish documentation
to GH Pages website. To publish such a documentation, we first
add the website remote to the Dotty github repo. If the remote
already exists, which is the case on a dirty workspace,
we get an error.

This PR should fix the failure to publish docs: https://github.com/lampepfl/dotty/runs/518302696?check_suite_focus=true

GH Actions mounts docker volumes and executes the jobs from
them. For some reason it doesn't clean these volumes
automatically after each run. We assume that each run happens
on a clean workspace and hence there are weird consequences
when this assumption is broken.

One of them, for example, is failure to publish documentation
to GH Pages website. To publish such a documentation, we first
add the website remote to the Dotty github repo. If the remote
already exists, which is the case on a dirty workspace,
we get an error.
@nicolasstucki nicolasstucki merged commit 97c3a1e into scala:master Mar 19, 2020
@nicolasstucki nicolasstucki deleted the clean-ghactions-workspace branch March 19, 2020 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants